Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add onBeforeRestoreAll and onRestoreAll #154

Closed
wants to merge 1 commit into from

Conversation

brendon
Copy link

@brendon brendon commented Jun 7, 2018

onBeforeRestore and onRestore are now granular and provide the target form. They also don't trigger if there is no data to restore for that particular form.

onBeforeRestoreAll and onRestoreAll operate like onBeforeRestore and onRestore used to.

No tests so far.

Potential to close #138 with more work.

`onBeforeRestore` and `onRestore` are now granular and provide the target form. They also don't trigger if there is no data to restore for that particular form.

`onBeforeRestoreAll` and `onRestoreAll` operate like `onBeforeRestore` and `onRestore` used to.

No tests so far.
@brendon
Copy link
Author

brendon commented Jun 7, 2018

I just wanted to float this concept before cleaning it up (documentation and tests). What do you think? I know it breaks the existing API but it's better to rename the methods to *All rather than call the new methods and callbacks onRestoreTarget IMO, but we could look at that as an alternative.

@brendon
Copy link
Author

brendon commented Aug 30, 2024

Ended up rolling my own solution in the end.

@brendon brendon closed this Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Suggestion : onBeforeRestore/onRestore could get array of restored fields
1 participant